Skip to content

routercap: capacity results (Envoy v1.30, 200 workers) - #808

Open
Chuang Wang (chuangw6) wants to merge 1 commit into
agent-substrate:mainfrom
chuangw6:bench/routercap-results
Open

routercap: capacity results (Envoy v1.30, 200 workers)#808
Chuang Wang (chuangw6) wants to merge 1 commit into
agent-substrate:mainfrom
chuangw6:bench/routercap-results

Conversation

@chuangw6

@chuangw6 Chuang Wang (chuangw6) commented Aug 8, 2026

Copy link
Copy Markdown
Collaborator

Fixes #665.

Findings from the first routercap study. Companion to #807 (the harness); this PR carries only the write-up and two report snapshots — review #807 for the tool, this one for the numbers. Best merged after #807.

Topology Sustained QPS
1 × 4c 9,000
1 × 8c 11,000
1 × 16c 13,000
2 × 4c 16,000
  • The wall is per-thread wake-up overhead, not CPU: wide arms die majority-idle, and capacity follows thread count, not the CPU limit.
  • One overloaded thread can fail the pod while container CPU reads 29% — monitor per-thread CPU, not the container average.
  • Scale out, not up: two 4-core replicas beat one 8-core pod 16k vs 11k on the same cores. Envoy v1.39 regressed 20-38% on every arm and stays off.

RESULTS.md carries the analysis; the two report.html files are self-contained chart snapshots (raw run data intentionally stays out of the repo).

🤖 Generated with Claude Code

@google-cla

google-cla Bot commented Aug 8, 2026

Copy link
Copy Markdown

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

One router pod sustains 9k/11k/13k QPS at 4/8/16 Envoy cores; the wall is
per-thread wake-up overhead, not CPU — wide arms die majority-idle. Two
4-core replicas beat one 8-core pod, 16k vs 11k on the same cores.
RESULTS.md carries the findings; the two report.html files are
self-contained chart snapshots of the underlying runs.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Measure atenet-router request capacity

2 participants